Configuring monitoring for virtualized servers

ABSTRACT

A method for configuring and maintaining external monitoring of one or more instances of a virtual machine within a virtualized computing environment. The method includes a computer processor monitoring a hypervisor. The method further includes a computer processor identifying a first list, wherein the first list is comprised of one or more monitoring templates respectively associated with one or more virtual machine types, and maintaining a second list comprised plurality of provisioned instances of virtual machines, wherein the second list also includes a first information respectively associated with the plurality of provisioned instances of virtual machines. The method further includes a computer processor compiling a third list and transmitting the third list to the monitoring system. The method further includes a computer processor receiving the third list and in response, a computer processor executing one or more monitoring functions based, at least in part, on the third list.

FIELD OF THE INVENTION

The present invention relates generally to the field of virtual machinemanagement, and more particularly to configuring and monitoring varioustypes of virtual servers.

BACKGROUND OF THE INVENTION

The size and complexity of computing networks and data centers hasrapidly grown, and the number of servers and other devices within thesedata centers has expanded greatly. Customer requirements changedintroducing multiple operating systems, optimized hardwareconfigurations, more rapid application development cycles, andunpredictable demand for computing resources. The cost, size, energyconsumption, and complexity of data centers built around individualservers, personal computers (PCs), storage devices, etc. becameprohibitive to maintain. Data centers have evolved away from individualservers and PCs to rack mounted “blade” server “farms” and RISC (reducedinstruction set computing) systems (computing clusters) and mostrecently “cloud” computing powered by mainframe computers that can be“virtualized” into entities and systems tailored to a customer'srequirements.

In system virtualization, multiple virtual entities are created and“hosted” within a physical system. Examples of virtual entities are:virtual servers, virtual storage, virtual networks including virtualprivate networks, virtual applications and operating systems, andvirtual clients. The physical system can be a stand-alone computer, oralternatively, a computing system utilizing clustered computers andcomponents. Virtual systems are independent operating environments thatuse virtual resources made up of logical divisions of physical resourcessuch as microprocessors, memory and input/output (I/O) adapters. Thissystem virtualization is implemented through some managingfunctionality, typically hypervisor technology. Hypervisors, also calledvirtual machine managers (VMMs), use a thin layer of code in software orfirmware to achieve fine-grained, dynamic resource sharing. Becausehypervisors provide the greatest level of flexibility in how resourcesare defined and managed, they are the primary technology for systemvirtualization.

Hypervisors provide the ability to divide physical computing systemresources into isolated logical partitions (also referred to as LPARs).Each logical partition operates like an independent computing systemrunning its own operating system (e.g., a virtual system, a virtualmachine). Operating systems utilized in this fashion include AIX®, IBM®i, Linux®, and the virtual I/O server (VIOS). Hypervisors allocatededicated processors (i.e., CPUs), I/O adapters, and memory to eachlogical partition. Additionally, hypervisors allocate shared orvirtualized resources (e.g., processors, memory, storage space, etc.) toeach virtual machine (VM). Unbeknownst to the virtual machines, thehypervisor creates a shared processor pool from which the hypervisorallocates virtual resources to the virtual machines as needed. In otherwords, the hypervisor creates virtual processors, virtual memory, etc.from physical resources so that virtual machines are capable of sharingthe physical resources while running independent operating environments.

The hypervisor also dynamically allocates and de-allocates dedicated orshared resources (such as processors, I/O, and memory) across LPARswhile the virtual machines are actively in use. This is known as dynamiclogical partitioning or dynamic LPAR and allows the hypervisor todynamically redefine all available system resources to reach optimumcapacity for each partition.

Data centers utilizing virtualization of computing resources range fromenterprise systems dedicated to a site within a company to distributedcomputing environments that sell access to their computing resources onan as-needed basis (e.g., cloud computing). Cloud computing is a modelof service delivery for enabling convenient, on-demand network access toa shared pool of configurable computing resources that may be rapidlyprovisioned and released with minimal management effort or interactionwith a provider of the service. For example, cloud computing allows acustomer to obtain data processing resources, such as networks, networkbandwidth, servers, processing, memory, storage, applications, virtualmachines, and services as a service on a temporary basis when needed.

A customer of cloud computing services may have its own data processingsystem resources. At certain times, the customer requires dataprocessing resources beyond those available in its computer network. Forexample, at certain times, the demand for data processing resourcesoutstrips the capability of the customer's computer network. At thesetimes, the response time of the customer's computer network for someapplications increases to unacceptable levels. At other times, thecustomer requires data processing applications that are not available onthe customer's own computer network. For example, the customer requires,at times, the use of data processing applications that are not part ofthe customer's core competency. At those times when the customerrequires data processing resources beyond its own, the customerpurchases such resources as a service, on a temporary basis, from aprovider of cloud computing services. For example, the customer mayobtain additional processing or storage resources or specificapplication functionality as a service on a temporary basis.

SUMMARY

According to an aspect of the present invention, there is a method,computer program product, and/or system for merging transactions forexecution by a database management system. A method for configuring andmaintaining external monitoring of one or more instances of a virtualmachine within a virtualized computing environment. The method includesa computer processor monitoring a hypervisor. The method furtherincludes a computer processor identifying a first list, wherein thefirst list is comprised of one or more monitoring templates respectivelyassociated with one or more virtual machine types. The method furtherincludes a computer processor maintaining a second list comprisedplurality of provisioned instances of virtual machines, wherein thesecond list also includes a first information respectively associatedwith the plurality of provisioned instances of virtual machines. Themethod further includes a computer processor compiling a third list andin response to compiling the third list, a computer processorcommunicating with a monitoring system, wherein communicating includes,at least in part, transmitting the third list to the monitoring system.The method further includes a computer processor responding to themonitoring system receiving the third list by executing one or moremonitoring functions based, at least in part, on the third list.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a virtualized computer environment, in an embodimentin accordance with the present invention.

FIG. 2 depicts a flowchart of the steps of a template managementprogram, in accordance with an embodiment of the present invention.

FIG. 3 depicts a flowchart of the steps of a monitoring activityprogram, in accordance with an embodiment of the present invention.

FIG. 4 depicts a flowchart of the steps of a cleanup program, inaccordance with an embodiment of the present invention.

FIG. 5 is a block diagram of components of a computer, in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments, in accordance with the present invention, recognize that acomputing resource running a hypervisor “provisions” (e.g., creates) avirtual machine (VM) server. Provisioning an instance of a VM serverincludes allocating computing resources, whether dedicated or shared(e.g., processors, memory, storage space, etc.), loading the appropriatesoftware (operating system, device drivers, middleware, andapplications), and changing the VM server's parameters (e.g., IPaddress, IP Gateway to find associated networks, etc.). The quickest,least disruptive and most automatable method to provision a VM server isby using “templates” accessed by the hosting computing resource. In anembodiment, templates may be standardized non-executable files used bycomputers and computer software as preformatted examples on which tobase other files. Other types of templates may be files that containpredefined information, variables, and/or lists of functions useable byother functions or programs to perform the same series of actions.Embodiments, in accordance with the present invention, address templatesas separate entities, associated entities, and/or incorporated entities.For example, a VM template is normally considered a separate entity.Monitoring configuration templates and configuration removal templatesare either associated with entities or incorporated within entities. Inone embodiment, a configuration removal template is linked or associatedwith a VM template to allow the resources allocated to an instance of aVM server, created from the VM template, to be released when theinstance of the VM server is de-provisioned. In another embodiment, amonitoring configuration template is incorporated within a VM templateto allow the instances of a VM server, based on the VM template, toaccess a specified group of monitoring functions.

Additionally, embodiments, in accordance with the present invention,recognize that within the diverse and complex environment of virtualizedcomputing, monitoring applications are vital to the stability andefficiency of the computing resource. Embodiments, in accordance withthe present invention, focus on the dynamic monitoring, configuring, andmodification of templates to set up and control the external monitoringof VM server instances. In an embodiment, the monitoring configurations(e.g., the program(s) assigned to monitor the instances of a VM servertype) are identified within the template for a VM server type (e.g.,incorporated monitoring configuration template). In another embodiment,a monitoring configuration template defines a suite of program(s) (e.g.,monitoring configuration) to monitor the instances of a VM server type.The monitoring configuration template is associated with the VM servertemplate and maintains the association with each VM server instancecreated from the VM server template. Some embodiments allow for dynamicpattern matching between the configuration of the current VM server,which do not include monitoring functions in some cases, and storedtemplates associated with VM servers containing instances of themonitoring programs or links to the external monitoring tools. Otherembodiments, in accordance with the present invention, recognize thatvariations in the monitoring data may occur based on instances of VMservers being distributed within a non-homogeneous computing environment(e.g., a distributed cluster, a cloud system, etc.) where theperformance of physical and virtualized resources differ.

Embodiments, in accordance with the present invention, will now bedescribed in detail with reference to the Figures. FIG. 1 illustrates avirtualized computing environment 100 for adding or updating monitoringtools to templates that are used for provisioning individual virtualmachine (VM) environments in an embodiment, in accordance with thepresent invention. Virtualized computing environment 100 includescomputer 102. Computer 102 is divided into multiple logical partitionsthat include logical partitions 103, 104, 105, 106, 107, 108, 109, and145. In the illustrated example, logical partitions 103, 104, 105, 106,107, 108, 109, and 145 each run an independent operating environment,such as an operating system (OS). Logical partitions 103, 104, 105, and106, respectively, execute OS 133, 134, 135, and 136, which is AIX®.Logical partition 145 runs OS 142, which is a virtual I/O server (VIOS).Logical partitions 107, 108, and 109, respectively, execute OS 137, 138,and 139, which is Linux®. Other operating environments and combinationsof operating environments may be included in logical partitions 103,104, 105, 106, 107, 108, 109, and 145. In various embodiments, anynumber of partitions may be created and may exist on separate physicalcomputers of a cloud computing system or a clustered computer system.

Communications from external network 110 are routed through SharedEthernet adapter (SEA) 141 on VIOS partition 145 to virtual adapters113, 114, 115, 116, 117, 118, and 119 on respective logical partitions103, 104, 105, 106, 107, 108, and 109. Communications from virtualadapters 113, 114, 115, 116, 117, 118, and 119 on respective logicalpartitions 103, 104, 105, 106, 107, 108, and 109 may be routed throughSEA 141 on VIOS partition 145 to external network 110. In an alternativeembodiment, physical network adapters are allocated to logicalpartitions 103, 104, 105, 106, 107, 108, 109, and 145.

Hypervisor 120 forms logical partitions 103, 104, 105, 106, 107, 108,109, and 145 from the physical or virtualized resources of computer 102through logical sharing of designated processors 150, storage disks 152,network cards 154, and/or memory 156 among logical partitions 103, 104,105, 106, 107, 108, 109, and 145. Hypervisor 120 performs standardoperating system functions and manages communication between logicalpartitions 103, 104, 105, 106, 107, 108, 109, and 145 via virtual switch147. Virtual switch 147 is a software program that allows one virtualmachine to communicate with another. Virtual switch 147 may be embeddedinto virtualization software or may be included in a server's hardwareas part of its firmware. Hypervisor 120 also includes template controland provisioning program 122 and instance decommissioning program 124.Template control and provisioning program 122 is software that controlsVM templates (e.g., creates, archives, deletes, modifies, etc.) andprovisions new virtual machines, herein identified as a VM server.Instance decommissioning program 124 releases provisioned resourcesassigned to a VM server when the VM server is decommissioned (e.g.,de-provisioned, deleted, destroyed). In an embodiment, template controland provisioning program 122 provisions new virtual machines withinlogical partitions 103, 104, 105, 106, 107, 108, 109 based on twooperating systems (OS). VM servers 103, 104, 105, and 106 execute theAIX® operating system. VM servers 103, 104, 105, and 106 are based oneither the same template or one or more different templates. VM servers103, 104, and 105 execute the Linux® operating system and are based oneither the same template or one or more different templates. In anotherembodiment, the VM servers provisioned from templates contain othersoftware, applications, and/or middleware as well as the operatingsystem. One of skill in the art will appreciate that in otherembodiments template control and provisioning program 122 and/orinstance decommissioning program 124 are located on a storage managementmodule connected to hypervisor 120. Alternatively, template control andprovisioning program 122 and/or instance decommissioning program 124execute on a separate computer from computer 102 within virtualizedcomputing environment 100.

System support programs 160 are connected to the hypervisor 120 andinclude dynamic configuration program 162, external monitoring tools166, and other ancillary programs (not shown). Dynamic configurationprogram 162 includes template management program 200, monitoringactivity program 300, cleanup program 400, and one or more lists ofmonitored systems (not shown). In an embodiment, system support programs160 stores the programs required, list(s) of monitored systems, or datacollected on storage disks 152. In another embodiment, system supportprograms 160 stores the programs required, one or more lists ofmonitored systems, or data collected on secondary storage 159 withinvirtualized computing environment 100. In an alternate embodiment,system support programs 160 execute on a separate computer from computer102 within virtualized computing environment 100.

In an embodiment, template control and provisioning program 122 operatesto automatically select and manage OS image templates when provisioninga virtual machine. The virtual machine definition is a template fileconsisting of a set of attributes that define a virtual machine (VM).The attributes include, for example, any name or identifying descriptionassigned to the virtual machine, an amount of memory requested by thevirtual machine, and a number of virtual processor units required by thevirtual machine. Additionally, a virtual machine definition can includedisks of a virtual machine, network interfaces of a virtual machine,input/output interfaces, any placement constraints and preferences forthe virtual machine, as well as any context of the virtual machineincluding files, disk images, or variables utilized by the virtualmachine. A VM template is a master copy (e.g., image) VM that isspecifically set aside to produce new VMs. A VM template is a specialtype of VM that is incapable of being activate. This allows a clean andstandard image from which other VMs are created. When a VM template ismodified, the modifications do not affect the executing VMs based on thetemplate. A new VM is created by modifying a VM based on an existing VMtemplate; the new VM is subsequently converted into a unique templatefor future use. Dynamic configuration program 162 interacts withtemplate control and provisioning program 122 to determine whichexternal monitoring tools 166 monitor the provisioned VM server type.For example, the monitoring configuration is associated with a VM servertemplate. In another example, the monitoring configuration isincorporated within the VM server template. In another embodiment,dynamic configuration program 162 updates the template selected bytemplate control and provisioning program 122 with the applicable suiteof monitoring programs (e.g., monitoring configuration) from externalmonitoring tools 166. In a different embodiment, template control andprovisioning program 122 is “slaved” to dynamic configuration program162 and awaits responses from dynamic configuration program 162 beforeprovisioning a VM server.

In an embodiment, template control and provisioning program 122 accessesVM image templates from a template library (not shown) on one or morestorage disks 152. In another embodiment, template control andprovisioning program 122 accesses the template library located onsecondary storage 159 outside of computer 102. In one example, secondarystorage 159 is disk storage attached via a dedicated storage areanetwork (SAN) to computer 102 or secondary storage 159 is providedthrough network file system (NFS) shares or tape provided by a serverattached via TCP/IP. In a cloud computing embodiment, template controland provisioning program 122 accesses image templates located on aremote system (not shown) accessed via external network 110. In anothercloud computing embodiment, the image templates are transmitted tovirtualized computing environment 100 from the remote system (not shown)via external network 110 as part of a system off-load (e.g., remotesystem is undergoing maintenance activity, experiencing a workloadspike, etc.).

Instance decommissioning program 124 operates to release resourcesassociated with a VM server when hypervisor 120 identifies an instanceof a VM server to decommission (e.g., de-provision, delete, or destroy).In an embodiment, the provisioned resources are released to computer102. In another embodiment, the provisioned resources are released tovirtualized computing environment 100.

Instance decommissioning program 124 operates to select a configurationremoval template (e.g., information) associated with the VM serveridentified for decommissioning by hypervisor 120. In an embodiment, theconfiguration removal template is incorporated within the VM servertemplate itself. In another embodiment, the configuration removaltemplate is a separate file in the template library (not shown) on oneor more storage disks 152. In another embodiment, instancedecommissioning program 124 accesses the template library located onsecondary storage 159 outside of computer 102. In one example, secondarystorage 159 is disk storage attached via a dedicated storage areanetwork (SAN) to computer 102. In another example, secondary storage 159is provided through network file system (NFS) shares or tape provided bya server attached via TCP/IP. In a cloud computing embodiment, instancedecommissioning program 124 accesses configuration removal templateslocated on a remote system (not shown) accessed via external network110. In another cloud computing embodiment, the configuration removaltemplates are transmitted to virtualized computing environment 100 fromthe remote system (not shown) via external network 110.

External network 110 can be, for example, a telecommunications network,a wide area network (WAN) such as the Internet, or a combination of thepreceding, and can include wired, wireless, or fiber optic connections.In general, external network 110 can be any combination of connectionsand protocols that will support communications between virtualizedcomputing environment 100 and a plurality of systems and computers (notshown).

External monitoring tools 166 is a collection of programs that monitorvarious parameters of the virtual machines (e.g., VM state, VMavailability, processor loading, memory utilization, bandwidth utilized,system performance, resource overcommitment, etc.) executing on computer102 within virtualized computing environment 100. As will be appreciatedby one skilled in the art, monitoring software ranges from “loadbalancers” to system monitors. Load balancer software is capable ofactivating and deactivating physical computing resources as demandchanges but also transferring virtualized resources from underutilizedVM servers to VM servers whose performance is impacted by insufficientresource allocations. System monitoring software is tailored to watchthe physical computing resource for issues signaling an impendinghardware failure and move VM servers to stable portions of the computingresource. Other varieties of system monitoring software focus onsecurity (e.g., isolating a VM trying to access data storage resourcenot allocated to them, locking-out an IP address or host name identifiedby an outside agency for “spamming” or distributing malware, etc.).Another type of system monitoring software watches the state of VMservers (e.g., paused, stopped, active, reset, resumed, suspended,resized, deleted, etc.) and the creation and modification of templatesfor VM servers. For example, external monitoring tools 166 can bebuilt-in tools supplied by the vendor of the virtualization software forcomputer 102 (e.g., accessible by system administrators), integratedtools installed on virtual computing environment 100 (e.g., accessibleby users), or third-party tools written by independent software vendors(ISVs). In an embodiment, external monitoring tools 166 create log fileslisting the monitored parameters and the value of the parameters withintime intervals. In another embodiment, external monitoring tools 166include an application programming interface (API) over which the usermay check the performance of one or more virtual machines, a VM servertype, an enterprise application (e.g., an electronic storefrontcomprised of a plurality of VM servers), etc., in real-time (e.g.,moving graph, circular gauge, bar chart, etc.).

FIG. 2 is a flowchart depicting operational steps of template managementprogram 200, executing within virtualized computing environment 100 ofFIG. 1 for monitoring the creation of instances of VM server anddynamically updating the template for the VM server and subsequentinstances to include monitoring software in an embodiment, in accordancewith the present invention. It should be appreciated by those of skillin the art that the changes to a VM template are highly dependent on thehardware, virtualized environment, operating system (e.g., hypervisor),and administrative controls of the hosting computer system. For example,one hosting computer system provides the user the tools and authority tomodify any aspect of a template. Another hosting computer systemrequires the user to first create and then modify a virtual machine,subsequently converting the virtual machine back to a template. Anotherhosting computer system provides a hybrid environment for templatemodification.

In step 202, template management program 200 detects hypervisor activity(e.g., one or more indications). In an embodiment, the detectedhypervisor activity is the creation of a VM server (e.g., templatecontrol and provisioning program 122 creates a VM server). The VM serveris either a new instance, or the VM server is a clone of a currentlyrunning VM server. For example, the user creates a new instance of a VMserver from a fully defined template, the user customizes a basictemplate supplied by the hosting computing system, or the userconfigures a VM server without using a template. In another embodiment,the detected hypervisor activity is associated with a change in statusof a currently running VM server or a change in the configuration of thecurrently running VM server. Changes in status (e.g., state) of a VMserver include pausing, stopping, starting, resetting, resuming,suspending, resizing, or decommissioning (e.g., deleting) of one or moreinstances.

In step 204, template management program 200 analyzes the userrequirements associated with the creation or maintenance of one or moreVM servers. For example, the user identifies which VM server types aremonitored. In another example, the user specifies whether identical VMserver instances, or incremental versions (e.g., a template creating aVM server with 50% of the resources) of the original VM server, areprovisioned or decommissioned based on performance thresholds. In anembodiment, the user configures a new VM server (e.g., host name, IPaddress, required computing resources, “mission critical” monitoring,etc.). In another embodiment, the user bases a VM server on a generic,partially configured template (e.g., from a list on cloud or hostingsystem), adjusts required computing resources, and specifies performancethreshold values for which the VM server is monitored.

In decision 206, template management program 200 checks whether thedetected hypervisor activity (step 202) is a request for provisioning anew VM server instance. If a new VM server instance is provisioned (yesbranch, decision 206), then template management program 200 analyses theprovisioning request (step 210).

In step 210, template management program 200 analyzes the VM server typeprovisioning request. For example, VM server types include AIX®, Linux®,Apache®, database, e-mail, etc. In an embodiment, template managementprogram 200 determines that the provisioned VM server type is based on atemplate. For example, the resources for provisioning the server areprivate node, 4 processors, 8 GB of RAM, 40 GB of disk storage (SANstorage), etc., and loaded with a software stack. In another embodiment,template management program 200 determines that the VM server type isnot associated with a template.

In step 212, template management program 200 searches for a VM servertemplate that matches the new server instance requirements. In anembodiment, template management program 200 searches for the VM servertemplate on storage disks 152 within computer 102 within virtualizedcomputing environment 100. In another embodiment, template managementprogram 200 searches secondary storage 159 within virtualized computingenvironment 100.

Step 212 also activates monitoring activity program 300 (step 302,trigger monitoring activities).

If template management program 200 does not locate a direct match forthe requested VM server type (no branch, decision 214), then templatemanagement program 200 directs dynamic configuration program 162(depicted in FIG. 1) to decision 304 (analyze provisioning request forVM server type) of monitoring activity program 300

In an embodiment, if template management program 200 locates a templatefor the requested VM server type (yes branch, decision 214), thentemplate management program 200 inspects the VM server type instance(s)based on the suite of monitoring tools, which are a subset of externalmonitoring tools 166 (depicted in FIG. 1), determined by monitoringactivity program 300.

In step 216, template management program 200 inspects the currentinstance(s) of the provisioned server type based on the suite ofmonitoring tools determined by monitoring activity program 300 (step336). For example, if the VM server was provisioned for four CPUs(central processor units) processing data, then the monitoring tool thattracks CPU performance also track four CPUs. In an embodiment, the VMserver type directly matches the suite of monitoring tools associatedwith the template, and template control and provisioning program 122starts the provisioned VM server. In another embodiment, the suite ofmonitoring tools assigned to the VM server type are based on acombination of pattern matching with other VM server templates and userrequirements (e.g., operating system, cost sensitive monitoring, etc.).

In an embodiment, template control and provisioning program 122(depicted in FIG. 1) is slaved to the activities of dynamicconfiguration program 162 (depicted in FIG. 1). Once the inspection ofVM server type instance(s) (e.g., provisioned VM servers) is verified,template control and provisioning program 122 activates the provisionedinstance(s) of the VM server type.

If no changes occur to the VM server template, or the suite ofmonitoring tools assigned to the VM server template subsequent to the VMserver instance provisioning and activation (no branch, decision 220),then template management program 200 activity is suspended.

If template management program 200 determines that the templateassociated with a VM server type was modified or the monitoring suiteassigned to a VM server type template was modified (yes branch, decision220), then the monitored instances associated with the modified VMserver type template are updated or replaced (step 222). In anembodiment, external monitoring tools 166 updates the parametersassociated with a VM server type. In another embodiment, the userrequirements for a given VM server type change, which is reflected in amodification to the VM server type template. In yet another embodiment,template management program 200 identifies that executing instances ofone or more VM servers types have been added to the list(s) of monitoredsystems. An updated template containing a suite of monitoring tools(e.g., monitoring configuration) is applied to the identified executinginstances.

In step 222, template management program 200 updates or replaces themonitored VM server instances(s). In an embodiment, the modifiedparameters of the VM server are updated while the virtual machine isexecuting. In another embodiment, the monitoring configuration ischanged. For example, the new monitoring configuration has a new name.The new name is changed associated with the executing VM servers. In yetanother embodiment, the VM server is first paused, the parameter changeapplied, and the VM server restarted. For example, the monitoringprograms defined within the VM server template change, and themonitoring parameters are similarly updated. It should be noted thatparameter changes that affect storage (e.g., DASD) increase thepossibility of data loss, so backing up data to persistent storage isadvisable prior to the storage parameter changes.

In yet another embodiment, if the template changes cannot be applied toa provisioned VM server, then the provisioned VM server requiresreplacement. In an example embodiment, the steps required to replace aVM server instance are: pause the original VM server instance; provisiona new instance based on the updated template; clone the operatingsystem, applications, and data to the new instance; start the newinstance and verify that the new instance is properly functioning; anddelete the original VM server instance. The aforementioned steps arerepeated for each affected instance of the VM server based on theupdated template. However, it should be appreciated by those of skill inthe art that changes to a VM template that are capable of being directlyapplied to an executing virtual machine are highly dependent on thehardware, virtualized environment, operating system and applicationsexecuting on the virtual machine, and the types of data being handled,etc.

Referring now to decision 206, if the detected hypervisor activity(e.g., an indication) is not a request for a new instance of a VM server(no branch, decision 206), then template management program 200ascertains to what the hypervisor activity is related.

In step 207, template management program 200 reviews and updates the VMserver configuration for one or more instances of a selected VM servertype. In an embodiment, the change in configuration changes theprovisioning parameters that are capable of being changed on anexecuting VM server. In another embodiment, the change occurs to thetemplate. In an embodiment, feedback from external monitoring tools 166(depicted in FIG. 1) applies parameter changes to the one or moreinstances of a VM server. For example, within the analyzed userrequirements (step 204) is a requirement to optimize response time.Parameters capable of modification on an executing VM server areinitiated at this step. In another embodiment, changes to a VM serverthat cannot be directly applied to an executing VM server require atemplate change and are subsequently instituted at step 222 of templatemanagement program 200. For example, external monitoring tools 166 arenot optimized for a cost sensitive computing application for the user.The suite of monitoring tools specified within the template is changedto track the VM server based on the requirement of cost.

If the hypervisor activity associated with a currently executinginstance of a VM server does not require a configuration change (nobranch, decision 230), then the hypervisor activity is checked todetermine if the executing instance(s) of a VM server aredecommissioning.

If the hypervisor activity associated with currently executinginstance(s) of a VM are decommissioned (yes branch, step 240), thentemplate management program 200 transfers control to cleanup program 400(depicted in FIG. 4).

If the detected hypervisor activity is not associated withdecommissioning of currently executing instance(s) of a VM (no branch,decision 240), then the hypervisor activity is analyzed separately (nobranch, decision 240).

In step 242, template management program 200 analyzes hypervisoractivity and responds accordingly. In an embodiment, the detectedhypervisor activity is a change in status of one or more instances of aVM server. For example, if a user's demand for computing resources ishighly variable, then it is advantageous to pause instances of a VMserver when demand drops and incrementally restart instances of the VMserver rather than decommissioning the instances. Dynamic configurationprogram 162 (depicted in FIG. 1) updates the one or more lists ofmonitored systems to identify the paused instances since a common suiteof tools is used for a template. As instances are restarted, the one ormore lists of monitored systems are subsequently updated. In anotherembodiment, template management program 200 determines that thehypervisor activity is unrelated to any VM servers on the one or morelists of monitored systems, and template management program 200 does notrespond and/or analyze this activity.

Referring now to decision 230, if the VM server configuration wasmodified (yes branch, decision 230), then template management program200 decides whether to save the configuration change to the currenttemplate (yes branch, decision 234) or to create a new template (nobranch, decision 234). In an embodiment, the user requirements determinewhether to save the configuration changes to the current template. Inone instance, the user's requirements define whether the decision isautomated. In another instance, the determination to save theconfiguration changes requires user intervention. For example, if theuser is testing various configurations, then the user indicates totemplate management program 200 to pause at decision 234 until the userhas reviewed the performance data collected by external monitoring tools166 (depicted in FIG. 1). In another embodiment, template managementprogram 200 determines, via dynamic pattern matching of the modifiedconfiguration to templates within the template library, whether anytemplates match the modified configuration and decides to save thecurrent modifications, as well as apply the modifications to othertemplates within the template library.

In step 236 (yes branch, decision 234), template management program 200saves the updates to the VM server configuration to the currenttemplate. In an embodiment, template management program 200 propagatesthe changes to the provisioned instances of the VM server. In anotherembodiment, template management program 200 only applies the updatedtemplate to new instances of the VM server type. In a differentembodiment, template management program 200 archives the currenttemplate before saving the updated configuration to the currenttemplate's file name. For example, the user needs to study the data fromexternal monitoring tools 166 (depicted in FIG. 1) over an extendedperiod. If the update template does not show a cost vs. performancebenefit, then the user decides to delete the current template andunarchive the original version of the template. When the user deletesthe template, dynamic configuration program 162 deletes the reference tothe template from the one or more lists of monitored systems.

Template management program 200 forwards the configuration changes totemplates from step 236 and step 237 to step 212 to trigger monitoringactivity program 300 (See FIG. 3) to review the template changes.Monitoring activity program 300 determines whether the new template isadded to the one or more lists of monitored systems. In an embodiment,monitoring activity program 300 determines a different suite ofmonitoring tools from external monitoring tools 166 (depicted in FIG. 1)is applied to the new template.

In step 237 (no branch, decision 234), template management program 200saves the updates to the VM server configuration to a new template. Inan embodiment, template management program 200 applies the new templateto new instances of the VM server type.

FIG. 3 is a flowchart depicting operational steps of monitoring activityprogram 300, executing within virtualized computing environment 100 ofFIG. 1. Monitoring activity program 300 determines suites of monitoringtools from the collection of external monitoring tools 166 (depicted inFIG. 1), applying the suites of monitoring tools to the appropriatetemplates, and identifying which VM server types and instances of VMservers that are on the list(s) of monitored systems.

In an embodiment, monitoring activity program 300 locates templatessimilar to the VM server provisioned by the user and, using dynamicpattern matching, identifies which predefined template matches theuser's requirements. Monitoring activity program 300 replaces (e.g.populates) variable values in the identified template with the variablevalues gathered from the hypervisor monitoring (e.g., provisioningrequirements). In another embodiment, monitoring activity program 300updates one or more monitored systems lists. For example, the one ormore monitored systems lists include: a VM server type, a user ID, atemplate name, a suite of monitoring tools assigned to a template,instances of a VM server, a status for each VM server instance, etc.Monitoring activity program 300 groups VM server type instances and theassociated suite of monitoring tools to reduce the overhead of theexternal monitoring tools.

In step 302, monitoring activity program 300 is triggered by templatemanagement program 200 searching for a VM server type template (step212). In an embodiment, the triggered monitoring activities includeaccessing the one or more lists of monitored systems, externalmonitoring tools 166 (depicted in FIG. 1), and template control andprovisioning program 122 (depicted in FIG. 1). In another embodiment,the triggering of monitoring activity is bypassed if the template is notfound for the provisioned instance of a VM server (no branch, decision214).

If a template for the provisioned VM server type was not found (nobranch, decision 304), then monitoring activity program 300 combines theanalysis of the provisioning requested for the VM server type and theuser's requirements to perform dynamic pattern matching (not shown) onthe template library. In an embodiment, the dynamic pattern matchingsearches for similar templates based on one or more of the following:operating system, host name, IP address, software stack, etc.

In step 306, monitoring activity program 300 generates a list oftemplates that are similar to the provisioned VM server type. In anembodiment, monitoring activity program 300 compares software stacksassociated with VM server templates in the template library to the VMserver being provisioned. In another embodiment, monitoring activityprogram 300 searches the template library for VM server templates basedon the provisioned resources.

In an embodiment based on a currently executing VM server as opposed toa new VM server instance request, monitoring activity program 300responds to the feedback from the external monitoring tools 166(depicted in FIG. 1) and/or the user from template management program200 (at step 207 in FIG. 2). For example, monitoring activity program300 searches for a VM server template that meets the user's performanceneeds at a lower unit cost.

If a similar VM server type template is not found (no branch, decision310), then monitoring activity program 300 notifies the user toconfigure a template for the current VM server provisioning request. Forexample, monitoring activity program 300 communicates with the user viaexternal network 110 using the user interface associated with creatingthe provisioning request for the cloud computing service provider.

In step 329, monitoring activity program 300 provides the user thecapability to convert/clone the currently provisioned VM server to atemplate file, manually add monitoring tools to the template, customizea VM server from a list generated by monitoring activity program 300(step 306), etc. Subsequently, monitoring activity program 300 transferscontrol to template management program 200 (prior to decision step 214).In an embodiment, the user creates a VM server template from the currentprovisioning request, via template control and provisioning program 122(depicted in FIG. 1), to clone the VM server or convert the VM server.The user also identifies that VM server instances based on the templateare added to the one or more lists of monitored systems and manuallyadds the monitoring tools from external monitoring tools 166 (depictedin FIG. 1) that will be associated with the template. In anotherembodiment, the user customizes a VM server template from the list ofsimilar VM server types generated by monitoring activity program 300(step 306). Monitoring activity program 300 removes instance-specificinformation from the templates in the list of similar templatespresented to the user and replaces the instance-specific informationwith “tokens.” For example, the token locations represent templateparameters, monitoring thresholds, or user specific information (e.g.,ports, hostnames, IP addresses, etc.), etc. Some or all of the tokensare customized to create a functional, new VM server template. Inanother embodiment, template and VM server creation, modification,cloning, converting, deleting, archiving, and unarchiving arefacilitated by a system support program 160 (not shown) or an API (notshown) within virtualized computing environment 100.

If monitoring activity program 300 finds similar templates for theprovisioned VM server (yes branch, decision 310), then monitoringactivity program 300 selects a template from the list of templates forsimilar VM server types.

In step 312, monitoring activity program 300 analyzes the parameters ofthe identified VM server templates and the monitoring data associatedwith the identified templates. Monitoring activity program 300 comparesthe analysis of the identified VM server templates to the user'srequirements. In an embodiment, monitoring activity program 300 selectsa VM server template to apply to the current provisioning request. Inanother embodiment, monitoring activity program 300 creates a rankedlist of VM server templates, saves the list, and associates it with auser, a hostname, an IP address, etc. For example, if on subsequentanalysis of the monitoring data, the automatically selected templatedoes not meet the user's requirements, then the user retrieves the savedlist of templates and reviews the available provisioning and performanceinformation. Based on the list of templates provided, the user selectsone of the templates to provision another VM server and repeats theprocess. In yet another embodiment, either monitoring activity program300 was unable to reconcile the user's requirements and the listedtemplates, or the user's requirements defined that the user controlledthe VM server template selection.

If no VM server template was selected (no branch, decision 320), thenmonitoring activity program 300 notifies the user (step 325).

In step 325, monitoring activity program 300 notifies the user that adecision is required in the selection of a VM server template. In anexample embodiment, monitoring activity program 300 communicates withthe user via external network 110 using the user interface associatedwith creating the provisioning request for the cloud computing serviceprovider. In another example embodiment, the user is not logged into thecomputer system hosting the user's VM servers at the time ofprovisioning the VM server. Monitoring activity program 300 reviews: theuser's requirements, system communication with the user, user's accountinformation, etc., to determine one or more methods to notify the user(e.g., e-mail, text message, instant message, automated phone call,etc.).

Monitoring activity program 300 provides the user with the list of VMserver templates similar to the user's provisioning request (step 306).In an embodiment, the user reviews the attributes of the listed VMserver templates and any associated monitoring information (e.g., suiteof monitoring tools, performance data, cost data, etc.). If the userselects a VM server template as the basis of a new VM server template,for the currently provisioned request, (yes branch, decision 327), thenmonitoring activity program 300 modifies the selected VM server templateto contain the user's information (e.g., user ID, account number, numberof instances to create, etc.), any unique variables from theprovisioning request (e.g., software stack, IP address, associateddatabases, URL links, etc.), and saves the modified template (e.g., anew name, a file associated with the provisioning request, etc.). Inanother embodiment, the user indicates to monitoring activity program300 that a VM server template on the generated list requiresauthorization prior to use.

If the user does not select a template from the list of similar VMservers or a listed template needs modification, monitoring activityprogram 300 (no branch, decision 327), then the user manually intervenesto create a template or customize a template (step 329).

Referring now to decisions 304 and 320, if a template is available forthe requested VM server type (yes branch, decision 304), monitoringactivity program 300 automatically selects a VM server template, or theuser selects a VM server template from the list of similar VM servertypes generated in step 306 (yes branch, decision 320), then monitoringactivity program 300 identifies the instance(s) of the VM server thatare associated with selected template (step 324).

In step 324, monitoring activity program 300 identifies the one or moreinstances of VM servers that are associated with the available orselected VM server type template. In an embodiment, the identified VMserver instances are executing on computer 102. In another embodiment,the identified VM server instances are distributed throughoutvirtualized computing environment 100. In yet another embodiment, theidentified instances are distributed within a non-homogeneous computingenvironment (e.g., a distributed cluster, a cloud system, etc.) wherethe performance of physical and virtualized resources differ. Thisaffects the accuracy of the data gathered by external monitoring tools166 (depicted in FIG. 1).

If the VM server template used for provisioning the current instance(s)of a VM server are not on the one or more lists of monitored systems (nobranch, decision 330), then template control and provisioning program122 (depicted in FIG. 1) proceeds with provisioning the instance(s) ofthe VM server.

If the VM server template used for provisioning the current instance(s)of a VM server are on the one or more lists of monitored systems (yesbranch, decision 330), then the new instance(s) are added to the one ormore lists of monitored systems (step 334).

In step 334, monitoring activity program 300 adds the new instance(s) ofthe VM server to a monitored systems list. In an embodiment, onemonitored systems list is assigned to computer 102 that contains theinformation about the monitored instances of VM servers under thecontrol of hypervisor 120. In another embodiment, the one or more listsof monitored systems track the instances of the monitored VM serveracross multiple hypervisors within virtualized computing environment100.

In step 336, monitoring activity program 300 determines a suite ofmonitoring tools, from the group of external monitoring tools 166(depicted in FIG. 1), which will be applied to the VM server type.Monitoring activity program 300 advises template management program 200which monitoring tools are defined for a VM server template so thatinstances of the VM server are inspected (step 216). In an embodiment,the template for the VM server type already contains a suite ofmonitoring tools. Monitoring activity program 300 reviews the userrequirements and determines whether the suite of monitoring toolsdefined in the VM server template meets the user's requirements. Basedon other parameters defined by the user in the user requirements, userprofile, or other documentation, monitoring activity program 300:updates the template the determined suit of monitoring tools, leaves thecurrent suite of monitoring tools as defined in the template, orcontacts the user to make the decision. In another embodiment, thetemplate for the VM server type does not have a suite of monitoringtools defined. Monitoring activity program 300 adds the determined suiteof monitoring tools to the VM server type template.

In step 338, monitoring activity program 300 notifies externalmonitoring tools 166 (depicted in FIG. 1) that a VM server type templatewill be monitored, the suite of tools used to monitor the template, andthe instances of the VM server that have been provisioned. In anembodiment, external monitoring tools 166 create log files listing themonitored parameters and the value of the parameters within timeintervals. In another embodiment, external monitoring tools 166 has anapplication programming interface (API) enabling the user to check theperformance of one or more virtual machines, a VM server type, anenterprise application (e.g., an electronic storefront comprised of aplurality of VM servers), etc. in real-time (e.g., moving graph,circular gauge, bar chart, etc.).

FIG. 4 is a flowchart depicting operational steps of cleanup program400, executing within virtualized computing environment 100 of FIG. 1.Cleanup program 400 determines which decommissioned VM serverinstance(s) are on the one or more lists of monitored systems, ensuresthat the associated resources are released, removes decommissionedinstance(s) from the one or more lists of monitored systems, andnotifies the external monitoring tools 166 (depicted in FIG. 1) of whichVM server instance(s) to cease monitoring. Cleanup program 400 performssimilar functions when a VM server template is archived or deleted.

In step 402, cleanup program 400 receives information from templatemanagement program 200 (step 240) that activity detected on hypervisor120 is related to a request to decommission one or more VM serverinstances. Cleanup program 400 determines which of the one or more VMserver instances decommissioned (e.g., VM state is changed to deleted)is on the one or more lists of monitored systems.

In step 404, cleanup program 400 identifies the configuration removaltemplate associated with the VM server decommissioning request torelease (e.g., de-provision) the resources allocated to the instance ofthe VM server. In an embodiment, the configuration removal informationis incorporated within the VM server template. Cleanup program 400obtains the configuration removal information from the VM servertemplate to create a configuration removal template for thedecommissioning request. In another embodiment, the configurationremoval template is a separate file that is associated with one or moreVM server templates.

In step 406, cleanup program 400 determines the identificationinformation and variable values for the decommissioned instance of a VMserver. In an embodiment, cleanup program 400 identifies the informationfor the named variables (e.g., IP address, hostname, etc.) specific tothe decommissioned instance(s) of the VM server. In another embodiment,cleanup program 400 identifies which suite of external monitoring tools166 (depicted in FIG. 1) are monitoring the decommissioned instance(s)of the VM server to facilitate the subsequent analysis, saving, and/ordeletion of the monitoring data.

In step 408, cleanup program 400 updates the configuration removaltemplate with the identification information and named variable valuesfor the VM server decommission request. In an embodiment, cleanupprogram 400 passes the updated configuration removal template toinstance decommissioning program 124 (depicted in FIG. 1) for the VMserver decommissioning request.

If cleanup program 400 determines that the decommissioned instance of aVM server is not on one or more lists of monitored systems (no branch,decision 410), then cleanup program 400 ends.

In step 412, if cleanup program 400 determined that the decommissionedinstance of a VM server is on one or more lists of monitored systems(yes branch, decision 410), then the instance(s) of the decommissionedVM server are removed from the one or more lists of monitored systems.In an embodiment, the decommissioned instance(s) are removed from theactive monitored systems list(s) and are saved in a log file for futurereference. In another embodiment, the one or more lists of monitoredsystems have a section identifying the VM server instance by the statusassociated with the instance (e.g., executing, paused, stopped,backing-up, decommissioned, etc.).

In step 420, cleanup program 400 notifies the suite of externalmonitoring tools 166 (depicted in FIG. 1) associated with the instanceof the VM server that the instance is decommissioned. In an embodiment,the external monitoring tools 166 end the data collection for thedecommissioned instance(s) of the VM server. In another embodiment,external monitoring tools 166 determine that user requirements wereassigned to the VM server type. For example, external monitoring tools166 transmit a log file to the user, via external network 110,describing the monitored behavior of the identified VM server type(e.g., latency change with load, resource usage, etc.). In anotherembodiment, cleanup program 400 handles the effects of archiving ordeleting VM server templates. For example, external monitoring tools 166store performance data associated with the archived VM server type onsecondary storage 159. In another example, external monitoring tools 166transmit the archived template and the performance data associated withthe archived VM server type to a cloud computing environment (not shown)via external network 110 providing the user a method to compare behaviorof virtualized computing environment 100 to the cloud computingenvironment.

In step 415, cleanup program 400 receives a request to archive or deletea VM server template from template control and provisioning program 122(depicted in FIG. 1) or system support programs 160 (depicted in FIG.1). Cleanup program 400 determines whether the archived or deleted VMserver template is on one or more lists of monitored systems.

If cleanup program 400 determines that the archived or deleted VM servertemplate is not on one or more lists of monitored systems (no branch,decision 417), then cleanup program 400 ends.

If cleanup program 400 determines that the archived or deleted VM servertemplate is on one or more monitored systems list(s) (yes branch,decision 417), then cleanup program 400 removes the archived or deletedVM server template from one or more lists of monitored systems (step419). In an embodiment, the archived or deleted VM server template isremoved from the active one or more lists of monitored systems and savedin a log file for future reference. In another embodiment, the one ormore lists of monitored systems have a section identifying the VM servertemplate by the status associated with the VM server (e.g., active,archived, deleted, etc.).

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(e.g., including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer-readablemedium(s) having computer-readable program code/instructions embodiedthereon.

It is understood in advance that although this disclosure includesreferences to cloud computing, implementations of the teachings recitedherein are not limited to the cloud computing environment. Rather, theillustrative embodiments are capable of being implemented in conjunctionwith any other type of computing environment now known or laterdeveloped.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that arerapidly provisioned and released with minimal management effort orinteraction with a provider of the service.

FIG. 5 depicts a block diagram of components of computer 102 in anillustrative embodiment, in accordance with the present invention. Itshould be appreciated that FIG. 5 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Computer 102 includes communications fabric 502, which providescommunications between computer processor(s) 504, memory 506, persistentstorage 508, communications unit 510, and input/output (I/O)interface(s) 512. Processor(s) 504 includes, at least in part,designated processors 150 depicted in FIG. 1 to be shared among logicalpartitions. Communications fabric 502 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric502 can be implemented with one or more buses.

Memory 506 and persistent storage 508 are computer readable storagemedia. In an embodiment, memory 506 includes random access memory (RAM)514 and cache memory 516. In general, memory 506 can include anysuitable volatile or non-volatile computer readable storage media.Software and data 522 are stored in persistent storage 508 for accessand/or execution by processor(s) 504 via one or more memories of memory506. With respect to computer 102, software and data 522 includestemplate control and provisioning program 122, instance decommissioningprogram 124, and system support programs 160 that include dynamicconfiguration program 162 and external monitoring tools 166. Dynamicconfiguration program 162 includes template management program 200,monitoring activity program 300, and cleanup program 400. Memory 506includes, at least in part, designated memory 156 depicted in FIG. 1 tobe shared among logical partitions.

Software and data 522 are stored in persistent storage 508 for executionby one or more of the respective processor(s) 504 via one or morememories of memory 506. Persistent storage 508 includes, at least inpart, designated storage disks 152 depicted in FIG. 1 to be shared bylogical partitions. In an embodiment, persistent storage 508 includes amagnetic hard disk drive. Alternatively, or in addition to a magnetichard disk drive, persistent storage 508 can include a solid state harddrive, a semiconductor storage device, read-only memory (ROM), erasableprogrammable read-only memory (EPROM), flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 508 may also be removable. Forexample, a removable hard drive may be used for persistent storage 508.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage508.

Communications unit 510, in these examples, provides for communicationswith other data processing systems or devices, including resources ofcomputer 102 and external network 110. In these examples, communicationsunit 510 includes one or more network interface cards. Communicationsunit 510 may provide communications through the use of either or bothphysical and wireless communications links. Software and data 522 may bedownloaded to persistent storage 508 through communications unit 510.Communications unit 510 includes, at least in part, designated networkcards 154 depicted in FIG. 1 to be shared by the logical partitions,preferably through VIOS partition 145.

I/O interface(s) 512 allows for input and output of data with otherdevices that may be connected to server computer 102. For example, I/Ointerface 512 may provide a connection to external devices 518 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 518 may also include portable computer readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data 522 may be stored onsuch portable computer readable storage media and loaded onto persistentstorage 508 via I/O interface(s) 512. I/O interface(s) 512 also connectto a display 520. In an embodiment, I/O interfaces are also shared amonglogical partition via VIOS partition 145.

Display 520 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method for configuring and maintaining externalmonitoring of one or more instances of a virtual machine within avirtualized computing environment, the method comprising: identifying,by one or more computer processors, a first list, wherein the first listis comprised of one or more monitoring templates respectively associatedwith one or more virtual machine types; maintaining, by one or morecomputer processors, a second list comprised of a plurality ofprovisioned instances of virtual machines executing on a hypervisor;compiling, by one or more computer processors, a third list comprised ofmonitored instances of provisioned virtual machines executing on thehypervisor, based, at least in part, on the first list and the secondlist, and wherein the provisioned virtual machines of the third list arerespectively associated with one or more monitoring templates;transmitting the third list to a monitoring system; and in response tothe monitoring system receiving the third list, executing, by one ormore computer processors, one or more functions to monitor thehypervisor, based, at least in part, on the third list.
 2. The method ofclaim 1, further comprising: monitoring, by one or more computerprocessors, the hypervisor.
 3. The method of claim 1, wherein the secondlist also includes a first set of information respectively associatedwith each of the plurality of provisioned instances of virtual machines,the first set of information includes information selected from thegroup consisting of: an ID of a provisioned virtual machine; a state ofa virtual machine; a virtual machine template; and a virtual machinetype identified within the first list.
 4. The method of claim 1, furthercomprising: detecting, by one or more computer processors, thehypervisor provisioning of a first instance of a first virtual machine;identifying, by one or more computer processors, a second set ofinformation associated with the first instance of the first virtualmachine; determining, by one or more computer processors, whether afirst virtual machine type is associated with the second set ofinformation of the first instance of the first virtual machine andwhether the first virtual machine type is included within the firstlist; and in response to determining that the first virtual machine typeassociated with the first instance of the first virtual machine isincluded within the first list, updating, by one or more computerprocessors, the third list based, at least in part, on second set ofinformation of the first instance of the first virtual machine and firstmonitoring template that is associated with the respective first virtualmachine type.
 5. The method of claim 1, further comprising: obtaining,by one or more computer processors, a first indication, from thehypervisor, that a change to a second set of information is associatedwith a second instance of a first virtual machine occurred; determining,by one or more computer processors, whether the change to the second setof information comprised a change in state and whether the change instate is deleted; determining, by one or more computer processors,whether an ID associated with the second instance of the first virtualmachine is identified within the third list; and in response todetermining that the change in state of the second instance of the firstvirtual machine is deleted and that the ID associated with the secondinstance of the first virtual machine is identified within the thirdlist, respectively removing, by one or more computer processors, thesecond instance of the first virtual machine from the second list andthe third list.
 6. The method of claim 5, further comprising: inresponse to determining that the change in state of the second instanceof the first virtual machine is deleted, identifying, by one or morecomputer processors, a configuration removal template associated withthe first virtual machine; determining, by one or more computerprocessors, a set of computing resources utilized by the second instanceof the first virtual machine utilizing the configuration removaltemplate associated with the first virtual machine and a monitoringfunction; and releasing, by one or more computer processors, the set ofcomputing resources utilized by the second instance of the first virtualmachine by communicating the configuration removal template and the setof computing resources utilized by the second instance of the firstvirtual machine to a decommissioning program associated with thehypervisor.
 7. The method of claim 6, wherein the set of computingresources utilized by the second instance of the first virtual machinediffers from computing resources provisioned by the hypervisor for thesecond instance of the first virtual machine based on one or moreactions of a load balancer that modifies the computing resources of thesecond instance of the first virtual machine during the execution of thesecond instance of the first virtual machine.
 8. A computer programproduct for configuring and maintaining external monitoring of one ormore instances of a virtual machine within a virtualized computingenvironment, the computer program product comprising: one or morecomputer readable storage media and program instructions stored on theone or more computer readable storage media, the program instructionsreadable/executable by one or more computer processors: programinstructions to identify a first list, wherein the first list iscomprised of one or more monitoring templates respectively associatedwith one or more virtual machine types; program instructions to maintaina second list comprised of a plurality of provisioned instances ofvirtual machines executing on a hypervisor; program instructions tocompile a third list comprised of monitored instances of provisionedvirtual machines executing on the hypervisor, based, at least in part,on the first list and the second list, and wherein the provisionedvirtual machines of the third list are respectively associated with oneor more monitoring templates; program instructions to transmit the thirdlist to a monitoring system; and program instructions to respond to themonitoring system receiving the third list, by executing one or morefunctions to monitor the hypervisor, based, at least in part, on thethird list.
 9. The computer program product of claim 8, furthercomprising: program instructions to monitor the hypervisor.
 10. Thecomputer program product of claim 8, wherein the second list alsoincludes a first set of information respectively associated with each ofthe plurality of provisioned instances of virtual machines, the firstset of information includes information selected from the groupconsisting of: an ID of a provisioned virtual machine; a state of avirtual machine; a virtual machine template; and a virtual machine typeidentified within the first list.
 11. The computer program product ofclaim 8, further comprising: program instructions to detect thehypervisor provisioning of a first instance of a first virtual machine;program instructions to identify a second set of information associatedwith the first instance of the first virtual machine; programinstructions to determine whether a first virtual machine type isassociated with the second set of information of the first instance ofthe first virtual machine and whether the first virtual machine type isincluded within the first list; and program instructions to respond todetermining that the first virtual machine type associated with thefirst instance of the first virtual machine is included within the firstlist, by updating the third list based, at least in part, on second setof information of the first instance of the first virtual machine andfirst monitoring template that is associated with the respective firstvirtual machine type.
 12. The computer program product of claim 8,further comprising: program instructions to obtain a first indication,from the hypervisor, that a change to a second set of information isassociated with a second instance of a first virtual machine occurred;program instructions to determine whether the change to the second setof information comprised a change in state and whether the change instate is deleted; program instructions to determine whether an IDassociated with the second instance of the first virtual machine isidentified within the third list; and program instructions to respond todetermining that the change in state of the second instance of the firstvirtual machine is deleted and that the ID associated with the secondinstance of the first virtual machine is identified within the thirdlist, by respectively removing the second instance of the first virtualmachine from the second list and the third list.
 13. The computerprogram product of claim 12, further comprising: program instructions torespond to determining that the change in state of the second instanceof the first virtual machine is deleted, by identifying a configurationremoval template associated with the first virtual machine; programinstructions to determine a set of computing resources utilized by thesecond instance of the first virtual machine utilizing the configurationremoval template associated with the first virtual machine and amonitoring function; and program instructions to release the set ofcomputing resources utilized by the second instance of the first virtualmachine by communicating the configuration removal template and the setof computing resources utilized by the second instance of the firstvirtual machine to a decommissioning program associated with thehypervisor.
 14. The computer program product of claim 13, wherein theset of computing resources utilized by the second instance of the firstvirtual machine differs from computing resources provisioned by thehypervisor for the second instance of the first virtual machine based onone or more actions of a load balancer that modifies the computingresources of the second instance of the first virtual machine during theexecution of the second instance of the first virtual machine.
 15. Acomputer system for configuring and maintaining external monitoring ofone or more instances of a virtual machine within a virtualizedcomputing environment, the computer system comprising: one or morecomputer processors; one or more computer readable storage media;program instructions stored on the computer readable storage media forreading/execution by at least one of the one or more computerprocessors, the program instructions comprising: program instructions toidentify a first list, wherein the first list is comprised of one ormore monitoring templates respectively associated with one or morevirtual machine types; program instructions to maintain a second listcomprised of a plurality of provisioned instances of virtual machinesexecuting on a hypervisor; program instructions to compile a third listcomprised of monitored instances of provisioned virtual machinesexecuting on the hypervisor, based, at least in part, on the first listand the second list, and wherein the provisioned virtual machines of thethird list are respectively associated with one or more monitoringtemplates; program instructions to transmit the third list to amonitoring system; and program instructions to respond to the monitoringsystem receiving the third list, by executing one or more functions tomonitor the hypervisor, based, at least in part, on the third list. 16.The computer system of claim 15, further comprising: programinstructions to monitor the hypervisor.
 17. The computer system of claim15, wherein the second list also includes a first set of informationrespectively associated with each of the plurality of provisionedinstances of virtual machines, the first set of information includesinformation selected from the group consisting of: an ID of aprovisioned virtual machine; a state of a virtual machine; a virtualmachine template; and a virtual machine type identified within the firstlist.
 18. The computer system of claim 15, further comprising: programinstructions to detect the hypervisor provisioning of a first instanceof a first virtual machine; program instructions to identify a secondset of information associated with the first instance of the firstvirtual machine; program instructions to determine whether a firstvirtual machine type is associated with the second set of information ofthe first instance of the first virtual machine and whether the firstvirtual machine type is included within the first list; and programinstructions to respond to determining that the first virtual machinetype associated with the first instance of the first virtual machine isincluded within the first list, by updating the third list based, atleast in part, on second set of information of the first instance of thefirst virtual machine and first monitoring template that is associatedwith the respective first virtual machine type.
 19. The computer systemof claim 15, further comprising: program instructions to obtain a firstindication, from the hypervisor, that a change to a second set ofinformation is associated with a second instance of a first virtualmachine occurred; program instructions to determine whether the changeto the second set of information comprised a change in state and whetherthe change in state is deleted; program instructions to determinewhether an ID associated with the second instance of the first virtualmachine is identified within the third list; and program instructions torespond to determining that the change in state of the second instanceof the first virtual machine is deleted and that the ID associated withthe second instance of the first virtual machine is identified withinthe third list, by respectively removing the second instance of thefirst virtual machine from the second list and the third list.
 20. Thecomputer system of claim 19, further comprising: program instructions torespond to determining that the change in state of the second instanceof the first virtual machine is deleted, by identifying a configurationremoval template associated with the first virtual machine; programinstructions to determine a set of computing resources utilized by thesecond instance of the first virtual machine utilizing the configurationremoval template associated with the first virtual machine and amonitoring function; and program instructions to release the set ofcomputing resources utilized by the second instance of the first virtualmachine by communicating the configuration removal template and the setof computing resources utilized by the second instance of the firstvirtual machine to a decommissioning program associated with thehypervisor.